Setting up a delegated TCP connection for hardware-optimized processing

ABSTRACT

A method of setting up a delegated connection for processing by an offload unit is described. The method comprises establishing a TCP connection and determining whether or not to delegate the TCP connection for processing by the offload unit, producing a delegated connection, and setting up the delegated connection by creating a delegated connection table entry. When frames are received on the delegated connection by the offload unit, the offload unit determines if user buffers are available. When user buffers are available, the offload unit uploads payload data to the user buffers. When user buffers are not available, the offload unit uploads a portion of the payload data to a buffer allocated in Operating System memory space.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority from commonly owned provisional U.S.Patent Application No. 60/476,570 entitled “HARDWARE-OPTIMIZED TCP/IP(HOT) PROCESSING,” filed Jun. 5, 2003, having common inventors andassignee as this application, which is incorporated by reference asthough fully set forth herein.

FIELD OF THE INVENTION

One or more aspects of the invention generally relate to TransmissionControl Protocol (TCP) processing, and more particularly to optimizationof TCP-based communications.

BACKGROUND

Conventional TCP processing is exemplified by systems and methodsdeveloped to accelerate data transfer between a client and a server.Software implementations executed on a host processor, e.g., CentralProcessing Unit (CPU), are comparatively inexpensive and slow comparedwith expensive dedicated hardware implementations designed to offloadTCP processing from the host processor.

FIG. 1 is a block diagram of an exemplary embodiment of a prior artcomputer system generally designated 100 including a CPU 110 and aNetwork Interface Card (NIC) 150. Computing System 100 may be a desktopcomputer, server, laptop computer, palm-sized computer, tablet computer,game console, cellular telephone, computer based simulator, or the like.A Bus 112 coupling CPU 110 to a System Controller 120 may be a frontside bus (FSB). Accordingly, Computing System 100 may be a hub-basedarchitecture, also known as an INTEL® hub architecture, where SystemController 120 is a memory controller hub and an I/O Bridge 140 iscoupled to System Controller 120 via a Hub-to-hub Interface 126. SystemController 120 is coupled to System Memory 130 via a Memory Bus 132. I/OBridge 140 includes a controller for Peripheral Component Interface(PCI) Bus 182 and may include controllers for a System Management Bus142, a Universal Serial Bus 144, and the like. I/O Bridge 140 may be asingle integrated circuit or single semiconductor platform. Examples ofSystem Controller 120 known in the art include INTEL® Northbridge.Examples of I/O Bridge 140 known in the art include INTEL® Southbridgeand NVIDIA® Media and Communications Processor (MCP) chips.

NIC 150 may share PCI bus 182 with one or more PCI Devices 180. NIC 150includes a PCI Interface 145, a Dedicated Processor 155, a Medium AccessController (MAC) 165, a Dedicated Memory 160, and an ETHERNET Interface170 to interface to an ETHERNET Network 172. Software Driver 119 for NIC150 communicates between NIC 150 and Application Program 117 executingon CPU 110. An Application Memory Space 125, TCP Stack Memory Space 145,and a Driver Memory Space 135 are allocated within System Memory 130.

Dedicated Processor 155 within NIC 150 is used for TCP processing inlieu of having CPU 110 execute TCP Stack 115 to perform TCP processing.Therefore NIC 150 offloads CPU 110, freeing CPU 110 processing cyclesfor other applications. Likewise, Dedicated Memory 160 replaces TCPStack Memory Space 145, freeing TCP Stack Memory Space 145 forallocation to other applications. However, NIC 150, including DedicatedMemory 160 and Dedicated Processor 155, is more costly than a softwareimplementation for TCP processing executed on CPU 110.

Therefore, there is a need for a partial hardware implementation thatoptimizes TCP processing by offloading some tasks from a host processorand reduces system cost compared with a dedicated hardwareimplementation.

SUMMARY

Various embodiments of a method of the invention include establishing aTCP connection and determining whether or not to delegate the TCPconnection for processing by hardware.

Various embodiments of a method of the invention for completing a slowstart sequence include disabling acknowledgement coalescing, setting acongestion window size to a value, and transmitting a frame.

Various embodiments of the invention include a system for setting up adelegated connection. The system includes a CPU configured to execute anapplication program and a TCP Stack. The TCP Stack is configured todetermine whether or not to delegate a TCP connection for processing byhardware. The system also includes a system memory coupled to the CPU.

The current invention involves new systems and methods for storing andaccessing delegated connection information.

BRIEF DESCRIPTION OF THE DRAWINGS

Accompanying drawing(s) show exemplary embodiment(s) in accordance withone or more aspects of the present invention; however, the accompanyingdrawing(s) should not be taken to limit the present invention to theembodiment(s) shown, but are for explanation and understanding only.

FIG. 1 is a block diagram of an exemplary embodiment of a prior artcomputing system including a host computer and a network interface card.

FIGS. 2A and 2B illustrate block diagrams of exemplary embodiments ofcomputing systems including a host computer in accordance with one ormore aspects of the present invention.

FIG. 3 illustrates the hardware optimized TCP subunit shown in FIGS. 2Aand 2B in accordance with one or more aspects of the present invention.

FIG. 4A illustrates an embodiment of a method of setting up a delegatedconnection in accordance with one or more aspects of the presentinvention.

FIG. 4B illustrates an embodiment of a method of receiving a frame inaccordance with one or more aspects of the present invention.

FIG. 4C illustrates an embodiment of a slow start sequence in accordancewith one or more aspects of the present invention.

FIG. 5A illustrates an embodiment of user buffers in the applicationmemory space shown in FIGS. 2A and 2B in accordance with one or moreaspects of the present invention.

FIG. 5B illustrates an embodiment of a user buffer descriptor inaccordance with one or more aspects of the present invention.

FIG. 5C illustrates an embodiment of legacy buffers in the softwaredriver memory space shown in FIGS. 2A and 2B in accordance with one ormore aspects of the present invention.

FIG. 5D illustrates an embodiment of a legacy buffer tag table inaccordance with one or more aspects of the present invention.

FIG. 5E illustrates an embodiment of a legacy buffer descriptor inaccordance with one or more aspects of the present invention.

FIG. 6A illustrates a conceptual diagram of a command ring fortransferring commands from an application program to an offload unit inaccordance with one or more aspects of the present invention.

FIG. 6B illustrates a conceptual diagram of a notification ring fortransferring connection information from an offload unit to anapplication program in accordance with one or more aspects of thepresent invention.

FIG. 6C illustrates a conceptual diagram of a receive descriptor ringfor transferring receive buffer information from an application programto an offload unit in accordance with one or more aspects of the presentinvention.

FIG. 6D illustrates a conceptual diagram of a transmit descriptor ringfor transferring transmit buffer information from an application programto an offload unit in accordance with one or more aspects of the presentinvention.

FIG. 7 illustrates a block diagram including a portion of the hardwareoptimized TCP subunit shown in FIG. 3 in accordance with one or moreaspects of the present invention.

FIG. 8A illustrates an embodiment of a method of processing a validframe in accordance with one or more aspects of the present invention.

FIG. 8B illustrates an embodiment of a method of processingout-of-sequence frames in accordance with one or more aspects of thepresent invention.

FIG. 8C illustrates an embodiment of a method of waiting for a userbuffer in accordance with one or more aspects of the present invention.

FIG. 8D illustrates an embodiment of a method of completing user bufferprocessing in accordance with one or more aspects of the presentinvention.

FIG. 9A illustrates an embodiment of a method of determiningnotifications in accordance with one or more aspects of the presentinvention.

FIG. 9B illustrates an embodiment of a method of synchronizing a userbuffer following legacy processing in accordance with one or moreaspects of the present invention.

FIGS. 10A and 10B illustrate formats used to represent data fortransmission in accordance with one or more aspects of the presentinvention.

FIGS. 11A and 11B illustrate embodiments of methods of editing outboundframes in accordance with one or more aspects of the present invention.

FIG. 11C illustrates an embodiment of a method of generatingacknowledgements for inclusion in a transmission in accordance with oneor more aspects of the present invention.

DISCLOSURE OF THE INVENTION

In the following description, numerous specific details are set forth toprovide a more thorough understanding of the present invention. However,it will be apparent to one of skill in the art that the presentinvention may be practiced without one or more of these specificdetails. In other instances, well-known features have not been describedin order to avoid obscuring the present invention.

FIGS. 2A and 2B illustrate block diagrams of exemplary embodiments ofComputing System 200 including CPU 110 and a Hardware Optimized TCP(HOT) Unit 250 in accordance with one or more aspects of the presentinvention. In FIG. 2A, offload unit HOT Unit 250 offloads some TCPprocessing from CPU 110. CPU 110 executes TCP Stack 215 which includescode to complete at least some of the TCP processing; specifically theTCP processing that is not performed by HOT Unit 250, as describedfurther herein. CPU 110 is coupled to a System Controller 120 via Bus112. System Controller 120 is coupled to System Memory 130 by System Bus132. System Memory 130 includes TCP Stack Memory Space 225, DriverMemory Space 235, and a Connection Table (CT) 245, described furtherherein. System Controller 120 is coupled to an I/O Controller 240 viaHub-to-hub Interface 126.

I/O Controller 240 includes a controller for PCI Bus 282 and may includecontrollers for System Management Bus (SMBus) 142, Universal Serial Bus(USB) 144, and the like. In an alternative embodiment, I/O Controllerincludes a controller for PCI Express bus. I/O Controller 240 alsoincludes HOT Unit 250, effectively decoupling HOT Unit 250 from devicescoupled to I/O Controller 240 via PCI Bus 282. Specifically, Hub-to-hubInterface 126 may be a high speed industry standard or proprietary buscoupling HOT Unit 250 to System Memory 130 via System Controller 120.Devices coupled to I/O Controller 240 share the bandwidth available onPCI Bus 282 which is typically lower than the bandwidth available onHub-to-hub Interface 126. The location of HOT Unit 250 within I/OController 240 results in lower latency between HOT Unit 250 and bothCPU 110 and System Memory 130 compared with latency between NIC 150 andCPU 110 shown in FIG. 1. Conventionally, low latency may be critical incommunicating between a NIC, such as NIC 150 and an application programsuch as a software stack via a Driver 219. Low latency is particularlyimportant for passing commands between NIC 150 and CPU 110, for example,to communicate that frame data stored in Driver Memory Space 135 isready to be copied to Application Memory Space 125. Furthermore, becauseHub-to-hub Interface 126 and Memory Bus 132 each support higherbandwidth than PCI Bus 282, HOT Unit 250 has higher bandwidth access toSystem Memory 130 than devices coupled to I/O Controller 240 via PCI Bus282. Higher bandwidth access to System Memory 130 enables HOT Unit 250to transfer received frames, sometimes referred to as “packets,” toApplication Memory Space 227 or Driver Memory Space 235 more quicklythan a device coupled to I/O Controller 240 via a lower bandwidth bussuch as PCI Bus 282.

HOT Unit 250 includes a controller interfacing to Input/Output Interface242. Input/Output Interface 242 may couple HOT Unit 250 to a physicallayer (PHY), e.g., 802.3 PHY, HPNA 1.0 PHY, HPNA 2.0 PHY, or the like.In an alternate embodiment a PHY is included within HOT Unit 250 andInput/Output Interface 242 is an ETHERNET interface such as GigabitETHERNET. I/O Controller 240 may be a single integrated circuit orsingle semiconductor platform.

FIG. 2B illustrates an alternate embodiment of Computing System 200including an Integrated Controller 220. Integrated Controller 220performs at least some of the functions performed by System Controller120 and I/O Controller 240 and includes HOT Unit 250. IntegratedController 220 may also include additional interface controllers (notshown), e.g., SMBus, USB, general purpose I/O (GPIO), integrated deviceelectronics (IDE), and the like.

TCP Stack 215 selects one or more TCP connections as delegatedconnections. A delegated connection is a TCP connection processed by HOTUnit 250 with minimal intervention by TCP Stack 215. Connections thatare not delegated or delegated connections that require specialprocessing are processed entirely or partially by TCP Stack 215. TCPStack 215 sets up a delegated connection by initializing an entry in adelegated connection table, as described further herein, within HOT Unit250 using Driver 255 stored within System Memory 130. Driver 255 iseffectively a translator between TCP Stack 215 and HOT Unit 250, issuingcommands to HOT Unit 250 as requested by TCP Stack 215. Driver 255 alsoinforms TCP Stack 215 when notifications are received from HOT Unit 250.Although communications between TCP Stack 215 and HOT Unit 250 areaccomplished using Driver 255, Driver 255 may not be explicitlyindicated henceforth.

Unlike the delegated connection table which only stores connection statedata for delegated connections, Connection Table 245 within SystemMemory 130 stores connection state data for all active connections.Therefore, TCP Stack 215 may assume processing of any delegatedconnection as requested by HOT Unit 250. Processing a delegatedconnection by TCP Stack 215 is referred to as “legacy processing.”

FIG. 3 is a block diagram of HOT Unit 250 shown in FIGS. 2A and 2B inaccordance with one or more aspects of the present invention. A directmemory access (DMA) interface within DMA Engine 310 interfaces one ormore subunits within either I/O Controller 240 or Integrated Controller220. The DMA interface is used to send and receive data between SystemMemory 130 and subunits within HOT Unit 250, and to send and receivecommands between CPU 110 and subunits within HOT Unit 250.

A Transmit Engine 320 includes subunits configured to parse and editoutbound frames, including acknowledgement insertion, and checksumcyclic redundancy check computation, producing outbound frames. ATransmit Interface 330 includes one or more buffers to store outboundframes for transmission and subunits configured to interface with a PHYcoupled to HOT Unit 250 via Input/Output Interface 242. In an alternateembodiment of HOT Unit 250, the PHY is integrated into HOT Unit 250.Transmit Engine 320 is coupled to a Delegated Connection Table (DCT)350, which stores connection state data for delegated connections.Delegated Connection Table 350 is a storage resource, e.g. random accessmemory (RAM), a register file, or the like. At least a portion of theconnection state data for delegated connections is also stored inConnection Table 245.

State information stored in Delegated Connection Table 350 may includean acknowledgement state, connection addresses, pointers to systemmemory buffers, connection tracking flags, event control information,transmit window size, receive window size, timestamp data, and the like.The acknowledgement state may include a sequence number of the nextexpected sequence number to be received, thresholds controlling thetimely generation of acknowledgements, and the like. Transmit Engine 320reads and writes portions of Delegated Connection Table 350 during frameprocessing using a connection table index, DCT index, to access an entryassociated with a delegated connection. Connection state data stored inthe entry is updated by TCP Stack 215, Transmit Engine 320, and ReceiveEngine 360 while the delegated connection is active, as described inrelation to FIG. 7.

Receive Interface 370 includes a subunit configured to interface withthe PHY coupled to HOT Unit 250 via Input/Output Interface 242. ReceiveInterface 370 also includes a receive FIFO (first-in first-out) bufferfor storing received frames that are destined for Receive Engine 360.Receive Engine 360 uploads either a partially processed frame or justthe TCP payload data to System Memory 130 via DMA Engine 310, asdescribed further herein.

Receive Engine 360 includes subunits configured to parse the incomingframe and determine whether or not the frame is valid, i.e., computingchecksums, verifying flags, and identifying the frame type, e.g., IP,UDP, TCP, and the like. When a parsed frame is not valid it is uploadedto a legacy buffer in Driver Memory Space 235 for legacy processing. Ifthe received frame contains an IP packet with a TCP segment, the TCPStack 215 is notified and copies the uploaded frame from the legacybuffer to Application Memory Space 227 after performing the required TCPprocessing.

When a parsed frame is determined to be valid, Receive Engine 360extracts the source IP address, TCP sequence number (SN), TCPacknowledgement (ACK) number, TCP source and destination port numbers,the TCP window size, the TCP header length, and the like. Parsed framesreceived on non-delegated connections are uploaded to legacy buffers inDriver Memory Space 235 for processing. A parsed frame that is receivedon a delegated connection and that is not a special case, e.g.,out-of-order sequence numbers, TCP Push flag set, and the like, isprocessed and the TCP payload data is uploaded to a user buffer inApplication Memory Space 227. Uploading TCP payload data directly toApplication Memory Space 227 is more efficient than uploading payloaddata through Driver Memory Space 235 since the TCP payload data does notneed to be subsequently copied from Driver Memory Space 235 toApplication Memory Space 227.

FIG. 4A is a flow diagram of method steps for setting up a delegatedconnection, in accordance with one embodiment of the present invention.In step 410 Computing System 200 establishes a TCP connection by way ofa 3-way handshake using a process known to those skilled in the art. Instep 412, TCP Stack 215 determines whether or not to delegate theconnection for processing by HOT Unit 250. TCP Stack 215 may determineto delegate a connection based on a characteristic of the delegatedconnection, such as a user-defined priority specified for the type ofconnection, a duration specified for the connection, a frame ratespecified for the connection, whether or not the connection will be usedfor applications likely to perform bulk transfers, the particular TCPports used by the connection, or the like.

If, in step 412 TCP Stack 215 determines the connection should not bedelegated for processing by HOT Unit 250, then in step 414 TCP Stack 215sets up an entry in CT 245 for processing the connection and proceeds tostep 422. If, in step 412 TCP Stack 215 determines the connection shouldbe delegated for processing by HOT Unit 250, then in step 416 TCP Stack215 issues a command to HOT Unit 250 setting up an entry in DCT 350 withconnection state data. In step 418 TCP Stack 215 determines whether ornot to issue a post receive buffers (PRB) command to HOT Unit 250, asfurther described herein, providing HOT Unit 250 with locations andsizes, in System Memory 130, of one or more user buffers. If, in step418 TCP Stack 215 determines a PRB command will be issued, then in step420 TCP Stack 215 issues a PRB command. If, in step 418 TCP Stack 215determines a PRB command will not be issued, then TCP Stack 215 proceedsto step 422. In step 422 connection setup is complete.

FIG. 4B is a flow diagram of method steps for receiving a frame, inaccordance with one embodiment of the present invention. In step 424 HOTUnit 250 receives a frame via Input/Output Interface 242 and maypartially process the frame producing a partially parsed frame andheader data. In step 425 HOT Unit 250 determines if the frame wasreceived on a delegated connection, and, if not, in step 440 HOT Unit250 uploads the partially processed frame including its complete set ofdata link layer and network layer protocol header data to one or morelegacy buffers. In step 442 TCP Stack 215 processes the partiallyprocessed frame uploaded to the legacy buffer.

If, in step 425 HOT Unit 250 determines the frame was received on adelegated connection, then in step 426 HOT Unit 250 completes parsing ofthe frame, extracting the TCP payload data. In step 427 HOT Unit 250determines if a user buffer is available, and, if so, then in step 428HOT Unit 250 uploads the TCP payload data to one or more user buffers.If, in step 427 HOT Unit 250 determines a user buffer is not available,then in step 430 HOT Unit 250 uploads a portion of the payload data to alegacy buffer and notifies TCP Stack 215. In one embodiment the portionis specified by a “startup limit” value stored in the entry in the DOT350 corresponding to the delegated connection. The “startup limit” is avariable that may take a maximum value equal to the maximum receiveframe size and a minimum value as determined by Application Program 217or TCP Stack 215.

In step 432 TCP Stack 215 processes the portion of the TCP payload datauploaded to the legacy buffer. In step 434 HOT Unit 250 determines ifone or more PRB commands issued by TCP Stack 215 for the delegatedconnection have been processed. In step 436 HOT Unit 350 uploads theremaining TCP payload data to one or more user buffers. If, in step 434HOT Unit 250 determines one or more PRB commands for the delegatedconnection have not been processed, then in step 438 HOT Unit 250uploads the remaining TCP payload data to a legacy buffer and notifiesTCP Stack 215. In an alternate embodiment, TCP Stack 215 completes step434 and in step 438 TCP Stack 215 instructs HOT Unit 250 to upload anyremaining TCP payload data to a legacy buffer.

In one embodiment, message signaled interrupts (MSIs) provide amechanism for HOT Unit 250 to use multiple interrupt vectors to signalits various interrupt sources. Utilizing MSIs enables efficiencies ininterrupt handling of the host. In one embodiment, Computing System 200uses up to eight interrupt vectors.

FIG. 4C is a flow diagram of method steps for completing a slow startsequence, in accordance with one embodiment of the present invention.The slow start and congestion avoidance algorithms are specified by theTCP protocol (as set forth in RFC 793, RFC 1122, and related documents)and are therefore well known by those skilled in the art. TCP uses slowstart and congestion avoidance to determine the available bandwidth fora given connection. Two variables, ssthresh (slow start threshold) andcwnd (congestion window) determine the behavior of a delegatedconnection. HOT Unit 250 uploads specific ACK information, including acount of the ACKs received, to TCP Stack 215. Rather than notifying TCPStack 215 for each received ACK, HOT Unit 250 may be configured by TCPStack 215 to coalesce ACKs, uploading ACKs to TCP Stack 215 at afrequency specified by TCP Stack 215. Coalescing ACKs permits HOT Unit250 to reduce the frequency at which HOT Unit 215 notifies TCP Stack 215of status for a delegated connection, which is expected to improveperformance in many cases. Specifically, utilization of CPU 110 istypically reduced because CPU 110 is not interrupted for each receivedACK. Including a count of the ACKs received permits TCP Stack 215 todetermine the number of ACKs that have been received for eachnotification to implement slow start and congestion avoidance.

In step 452 Application program 217 sets cwnd to 1 segment for thedelegated connection and TCP Stack 215 outputs a transmit bufferdescriptor to HOT Unit 250, as described further herein in relation toFIG. 6D. In step 454 HOT Unit 250 determines if an ACK was received fromthe destination. HOT Unit 250 remains in step 454 until the ACK isreceived and then HOT Unit 250 notifies TCP Stack 215 and proceeds tostep 456. In one embodiment HOT Unit 250 outputs a count of receivedACKs to TCP Stack 215 and TCP Stack 215 may compute the number of ACKsreceived for a delegated connection between each notification.

In step 456 TCP Stack 215 determines if cwnd is greater than or equal tossthresh for the delegated connection, and if so, then in step 458 TCPStack 215 exponentially increases, i.e., opens, the cwnd based on thenumber of ACKs received for the delegated connection. In step 458 TCPStack 215 also outputs a transmit buffer descriptor to HOT Unit 250 andreturns to step 454.

In one embodiment in step 458 TCP Stack 215 configures HOT Unit 250 tonotify TCP Stack 215 for each received ACK. In an alternate embodimentTCP Stack 215 configures HOT Unit 250 to notify TCP Stack 215 for acount of received ACKs, thereby performing some ACK coalescing. If, instep 456 TCP Stack 215 determines ssthresh is less than cwnd for thedelegated connection, then in step 460 TCP Stack 215 is in congestionavoidance phase. When congestion avoidance is used cwnd opens linearly,until either cwnd equals the maximum transmit window size or packets aredropped.

FIG. 5A illustrates an embodiment of user buffers stored in ApplicationMemory Space 227 shown in FIGS. 2A and 2B in accordance with one or moreaspects of the present invention. Each user buffer, such as a UserBuffer 510, a User Buffer 512, or a User Buffer 514, is allocated inApplication Memory Space 227 to receive payload data uploaded by HOTUnit 250. A physical memory address, such as User Buffer Address 515indicates the location of a User Buffer 510 in Application Memory Space227. Likewise, User Buffer Address 520 indicates the location of UserBuffer 512 and User Buffer Address 525 indicates the location of UserBuffer 514. User buffers may be stored in physically contiguous memorylocations within Application Memory Space 227 or in physicallynon-contiguous memory locations within Application Memory Space 227.

FIG. 5B illustrates an embodiment of a user buffer descriptor inaccordance with one or more aspects of the present invention. Each userbuffer has a corresponding length determined by the number of byteswhich can be stored within the user buffer. For example the length of aUser Buffer 510 is a User Buffer Length 535. A user buffer descriptor isa data structure including a user buffer address, such as a User BufferAddress 515 and a corresponding user buffer length, such as a UserBuffer Length 535. In an alternate embodiment a user buffer descriptormay include descriptor flags indicating any special handling, and thelike. The user buffer descriptor flags can include, among other bits, abit requesting that HOT Unit 350 issue a notification command whenpayload data is uploaded to the user buffer included in the PRB command.

In a further alternate embodiment a user buffer descriptor may includeany combination of a user buffer address, a user buffer length, and auser buffer end address. As previously mentioned, user bufferdescriptors are provided to HOT Unit 250 by TCP Stack 215 using a PRBcommand. Providing physical memory addresses located in ApplicationMemory Space 227 to HOT Unit 250 enables HOT Unit 250 to upload payloaddata directly to Application Memory Space 227.

Application Program 217 manages user address space which is a virtuallycontiguous address space allocated by an operating system. WhenApplication Program 217 transfers the user address space information toTCP Stack 215, TCP Stack 215 requests that the operating system lock thememory corresponding to the user buffer address space. The operatingsystem locks the amount of memory and returns one or more physicaladdresses (and lengths) corresponding to physically contiguous portionsof System Memory 130 to TCP Stack 215. The physical address space,accessed by HOT Unit 250, is managed by TCP Stack 215 and is notnecessarily physically contiguous. TCP Stack 215 translates between theuser address space and the physical address space. In an alternateembodiment Driver 255 translates between the user address space andphysical address space.

FIG. 5C illustrates an embodiment of legacy buffers stored in DriverMemory Space 235 shown in FIGS. 2A and 2B in accordance with one or moreaspects of the present invention. Each legacy buffer, such as a LegacyBuffer 550, a Legacy Buffer 552, or a Legacy Buffer 554, is allocated inDriver Memory Space 235 to receive partially processed frames uploadedby HOT Unit 250. A physical memory address, such as a Legacy BufferAddress 555 indicates the location of Legacy Buffer 550 in Driver MemorySpace 235. Likewise, a Legacy Buffer Address 560 indicates the locationof Legacy Buffer 552 and Legacy Buffer Address 565 indicates thelocation of Legacy Buffer 554. Legacy buffers may be stored incontiguous memory locations within Driver Memory Space 235 or innon-contiguous memory locations within Driver Memory Space 235.

FIG. 5D illustrates an embodiment of a Legacy Buffer Tag Table 590 inaccordance with one or more aspects of the present invention. Eachlegacy buffer address is associated with a unique tag. For example,Legacy Buffer Address 555 is associated with Tag 575, Legacy BufferAddress 560 is associated with Tag 580, and Legacy Buffer Address 565 isassociated with Tag 585. Legacy Buffer Tag Table 590 is maintained byDriver 255 and may be stored in Driver Memory Space 235 in oneembodiment or in TCP Stack Memory Space 225 in another embodiment.

FIG. 5E illustrates an embodiment of a legacy buffer descriptor inaccordance with one or more aspects of the present invention. Eachlegacy buffer has a corresponding length determined by the number ofbytes which can be stored within the legacy buffer. For example thelength of Legacy Buffer 550 is a Legacy Buffer Length 570. In analternate embodiment, the lengths of all legacy buffers are equal. Alegacy buffer descriptor is a data structure including a legacy bufferaddress, such as Legacy Buffer Address 555, a corresponding legacybuffer length, such as Legacy Buffer Length 570, and a correspondingtag, such as Tag 575. In an alternate embodiment a legacy bufferdescriptor may include any combination of a legacy buffer address, alegacy buffer length, a tag, and a legacy buffer end address. Legacybuffer descriptors are provided to HOT Unit 250 by Driver 255 using areceive (buffer) descriptor ring, as further described in relation toFIG. 6C.

Communication between Driver 255 and HOT Unit 250 is accomplishedthrough data structures stored in Driver Memory Space 235. A ring is adata structure that includes several entries, as described furtherherein. A ring is organized as a circular queue of the entries with apointer used by Driver 255 and another pointer used by HOT Unit 250.Each ring is stored in contiguous physical memory in Driver Memory Space235.

FIG. 6A illustrates a conceptual diagram of a Command Ring 601 fortransferring commands from Driver 255 to HOT Unit 250 and fortransferring status from HOT Unit 250 to Driver 255. Command Ring 601 isused to initialize delegated connection entries in DCT 350 and toprovide user buffer descriptors to DCT 350. Command Ring 601 includesseveral entries, each entry shown in FIG. 6A as a Command Ring Entry603. Each Command Ring Entry 603 includes an “own” bit indicating theentry is owned by either HOT Unit 250 or Driver 255. At startup, the“own” bit in each entry is initialized to indicated the entries areowned by Driver 255 and a Command Write Pointer 607 and Command ReadPointer 605 are the same entry in Command Ring 601. When TCP Stack 215writes a command to an entry via Driver 255, the “own” bit is set toindicate that the entry is owned by Hot Unit 250 and Command WritePointer 607 is modified to point to the next Command Ring Entry 603within Command Ring 601. When HOT Unit 250 reads and completesprocessing, an entry addressed by Command Read Point 605 the “own” bitis set to indicate that the entry is owned by Driver 255. Command ReadPointer 605 is not permitted to pass Command Write Pointer 607. Wheneither Command Read Pointer 605 or Command Write Pointer 607 reaches thelast entry in Command Ring 601, the pointer wraps to the first entry inCommand Ring 601. Those skilled in the art understand that othermechanisms may be used to communicate commands to HOT Unit 250, e.g., alinked list of commands, a FIFO, a shared memory scheme, or the like.

In addition to the “own” bit, each Command Ring Entry 603 includes acommand field, a DCT index, command-specific control and/or statusinformation, command-specific data, and the like. As was previouslymentioned, the DCT index identifies an entry in DCT 350 corresponding toa delegated connection. The command field includes a command identifierfor a command such as, a PRB command, an update table entry (UTE)command, an invalidate table entry (ITE) command, a dump connectionbuffer table entry (DCBTE) command, and the like. When a command iswritten by Driver 255 the command specific control/status informationincludes command specific control. When a command is read and updated byHOT Unit 350, the command specific control/status information is updatedto include command specific status. The command specific data is writtenby Driver 255 and read by HOT Unit 350, as described further herein.

The PRB command is used by Application Program 217 to pass user bufferdescriptors to HOT Unit 350, via TCP Stack 215 and Driver 255. Each userbuffer descriptor indicates a physical address in Application MemorySpace 227 for HOT Unit 350 to upload payload data to. TCP Stack receivesone or more user addresses and determines corresponding physicaladdresses for inclusion in a user buffer descriptor. TCP Stack 215 canpost one or more user buffer descriptors via Driver 255 using a PRBcommand, on behalf of Application Program 217, for a single delegatedconnection table entry. Driver 255 includes the number of user buffersin the command-specific control and/or status information field within aPRB command. Because Driver 255 does not have the information necessaryto determine how many of the previously posted user buffers have beenuploaded to by HOT Unit 350, HOT Unit 350 writes a value in thecommand-specific control and/or status information field indicating thenumber of user buffers accepted from the PRB command.

The command-specific control and/or status information field in a PRBcommand also includes a “sync” bit. TCP Stack 215 requests Driver 255 towrite the “sync” bit when a notification command including an assertedlegacy flag, as described further herein in relation to FIG. 9B, hasbeen received from HOT Unit 350 via Notification Ring 611.

The command-specific data field in a PRB command constructed by Driver255 includes a starting TCP sequence number corresponding to the firstbyte of the first buffer posted in the PRB command, a user bufferdescriptor for each user buffer included in the PRB command, and thelike. A user buffer descriptor includes a physical address specifying alocation in Application Memory Space 227, the length of the user buffer,descriptor flags indicating any special handling, and the like.

The UTE command is used by Driver 255 to update an entry in DCT 350 andis used to setup a delegated connection and update connection data whilea delegated connection is active. The ITE command is used to invalidatea delegated connection. When HOT Unit 250 receives an ITE command itwaits, if necessary, for processing by Transmit Engine 320 and ReceiveEngine 360 to complete (while blocking any new TCP processing fromstarting) before clearing the delegated connection corresponding to theDCT index specified in the ITE command. The DCBTE command causes HOTUnit 350 to upload a portion of an entry specified by the DCT indexincluded in the DCBTE command to a legacy buffer.

Driver 255 can access Command Ring 601 without interfering with transmitor receive processing for the PRB command. This permits Driver 255 toprovide HOT Unit 350 with new user buffers in a timely manner, improvingthe likelihood that receive frames can be accepted by HOT Unit 350rather than blocked.

FIG. 6B illustrates a conceptual diagram of a Notification Ring 611 fortransferring event notification descriptors from HOT Unit 250 to Driver255. Notification Ring 611 carries connection information from HOT Unit250 to TCP Stack 215 via Driver 255. Those skilled in the art understandthat other mechanisms may be used to communicate information from HOTUnit 250 to TCP Stack 215, e.g., a linked list of notificationdescriptors, a FIFO, a shared memory scheme, or the like.

Notification Ring 611 includes several entries, each entry shown in FIG.6B as a Notification Ring Entry 613. Each Notification Ring Entry 613includes an “own” bit indicating the entry is owned by either HOT Unit250 or Driver 255. At startup the “own” bit in each entry is initializedto indicated the entries are owned by HOT Unit 250 and a NotificationWrite Pointer 617 and Notification Read Pointer 615 are the same entryin Notification Ring 611. When Hot Unit 250 writes a notificationdescriptor to an entry via Driver 255, the “own” bit is set to indicatethat the entry is owned by Driver 255 and Notification Write Pointer 615is modified to point to the next Notification Ring Entry 613 withinNotification Ring 611. When Driver 255 reads and has completedprocessing an entry addressed by Notification Read Pointer 617, the“own” bit is set to indicate that the entry is owned by HOT Unit 250.Notification Read Pointer 617 is not permitted to pass NotificationWrite Pointer 615. When either Notification Read Pointer 617 orNotification Write Pointer 615 reaches the last entry in NotificationRing 611, the pointer wraps to the first entry in Notification Ring 611.

In addition to the “own” bit, each Notification Ring Entry 613 includesa notification flags field, a DCT index, an optional tag that, ifpresent, provides a reference to a particular legacy buffer, the nextexpected sequence number, the highest received ACK number, the mostrecently received transmit window size, current TCP timestamp, and thelike, for the delegated connection specified by the DCT index. Thenotification flags field includes a “legacy” flag, a “push notification”flag, a “duplicate ACK” flag, a “sequence number threshold” flag, an“ACK threshold” flag, a “request buffer” flag, and the like. The“legacy” flag is asserted when payload data or partially parsed framedata has been uploaded by HOT Unit 250 to a legacy buffer. The functionof the “push notification” flag, the “duplicate ACK” flag, the “sequencenumber threshold” flag, the “ACK threshold” flag, and the “requestbuffer” flag are described in relation to FIG. 9A.

The optional tag is included when HOT Unit 250 uploads payload data orpartially parsed frame data to a legacy buffer, as described furtherherein in relation to FIG. 8C. The tag is received from Driver 255 viathe receive descriptor ring, described further herein, and is used toassociate a given notification with the legacy buffer into which payloaddata or partially parsed frame data was uploaded. Driver 255 may use thetag received with a notification to locate the legacy buffer in DriverMemory Space 235 by reading the entry in Legacy Buffer Tag Table 590associated with the tag.

HOT Unit 250 can use Notification Ring 611 to inform Driver 255 in atimely manner of connection conditions requiring further processing byDriver 255 with minimal impact, if any, on transmit or receiveprocessing by HOT Unit 250. The operation of the Notification Ring 611permits Driver 255 to provide HOT Unit 350 with new user buffers in atimely manner, improving the likelihood that received frames can beaccepted by HOT Unit 350 rather than blocked.

FIG. 6C illustrates a conceptual diagram of a Receive Descriptor Ring621 for transferring receive buffer information from TCP Stack 215 viaDriver 255 to HOT Unit 250 in accordance with one or more aspects of thepresent invention. Receive Descriptor Ring 621 is used to provide legacybuffer descriptors to HOT Unit 250. Several types of data can beuploaded by HOT Unit 250 to legacy buffers, including non-TCP frames,frames received on non-delegated connections, frames received ondelegated connections which included an anomaly (unexpected flags,out-of-sequence, invalid checksum, and the like), and connection datauploaded from DCT 350. Those skilled in the art understand that othermechanisms may be used to provide buffer descriptors to HOT Unit 250,e.g., a linked list of buffer descriptors, a FIFO, a shared memoryscheme, or the like.

Receive Descriptor Ring 621 includes several entries, each entry shownin FIG. 6C as a Receive Descriptor Ring Entry 623. Each ReceiveDescriptor Entry 623 includes an “own” bit indicating the entry is ownedby either HOT Unit 250 or Driver 255. Functionality of the “own” bit isas described in relation to FIG. 6A. Functionality of Receive DescriptorWrite Pointer 627 is the same as Command Write Pointer 607 andfunctionality of Receive Descriptor Read Pointer 625 is the same asCommand Read Pointer 605.

In addition to the “own” bit, each Receive Descriptor Ring Entry 623includes a legacy buffer descriptor, a receive control and/or statusfield, and the like. As previously described in relation to FIG. 5E, alegacy buffer descriptor includes a physical address specifying alocation in Driver Memory Space 235, a legacy buffer length, and anoptional tag.

When a Receive Descriptor Ring Entry 623 is written by Driver 255 theReceive Descriptor Ring Entry 623 can include, among other bits, a bitrequesting that HOT Unit 350 issue an interrupt when data is uploaded tothe legacy buffer specified in the Receive Descriptor Ring Entry 623.When a Receive Descriptor Ring Entry 623 is read and updated by HOT Unit350, the receive control and/or status information is updated to includeconnection status when payload data or parsed frame data is uploaded toa legacy buffer. The receive control and/or status information writtenby HOT Unit 350 for a non-delegated connection upload to a legacy buffercan include an end of receive frame indicator, exceeded maximum framesize indicator, and the like. The receive control and/or statusinformation written by HOT Unit 350 for a delegated connection upload toa legacy buffer can include startup buffer indicator, user buffer notavailable indicator, end of receive frame, out-of-range ACK receivedindicator, and the like.

FIG. 6D illustrates a conceptual diagram of Transmit Descriptor Ring 631for transferring transmit buffer information from TCP Stack 215 viaDriver 255 to HOT Unit 250 in accordance with one or more aspects of thepresent invention. Transmit Descriptor Ring 631 is used to providetransmit buffer descriptors to HOT Unit 250. Those skilled in the artunderstand that other mechanisms may be used to provide bufferdescriptors to HOT Unit 250, e.g., a linked list of buffer descriptors,a FIFO, a shared memory scheme, or the like.

Transmit Descriptor Ring 631 includes several entries, each entry shownin FIG. 6D as a Transmit Descriptor Ring Entry 633. Each TransmitDescriptor Entry 633 includes an “own” bit indicating the entry is ownedby either HOT Unit 250 or Driver 255. Functionality of the own bit is asdescribed in relation to FIG. 6A. Functionality of Transmit DescriptorWrite Pointer 637 is the same as Command Write Pointer 607 andfunctionality of Transmit Descriptor Read Pointer 635 is the same asCommand Read Pointer 605.

In addition to the “own” bit, each Transmit Descriptor Ring Entry 633includes a transmit buffer descriptor, DCT index, transmit-specificcontrol, a transmit control/status field, a transmit buffer byte count,and the like. A transmit buffer descriptor includes a physical addressspecifying a location in Application Memory Space 227 or TCP StackMemory Space 225 where frame data for transmission is stored. HOT Unit250 reads the frame data for transmission from Driver Memory Space 235using the physical address. The transmit-specific control can include arequest for Transmit Engine 320 to save the sequence number of the firstbyte of a frame in DCT 350. When an ACK is received for the frame, HOTUnit 250 may generate a notification command.

The transmit control and/or status field written by Driver 255 caninclude an end of transmit frame indicator, a bit enabling TCPsegmentation, one or more bits enabling TCP checksum computation in HOTUnit 250, a maximum segment size for use during TCP segmentation, andthe like. When a Transmit Descriptor Ring Entry 633 is read and updatedby HOT Unit 250, the transmit-specific control and/or status informationis updated to include transmit-specific status. Transmit-specific statuscan include a loss of carrier indicator, a transmit retry count, a retryerror, and the like.

FIG. 7 is a block diagram including a portion of the of HOT Unit 250shown in FIG. 3 in accordance with one or more aspects of the presentinvention. DCT 350 includes a CMD Unit 710 for processing commandsreceived from Driver 255 via Command Ring 601. Delegated connectioninformation is stored within DCT 350 in a Connection Buffer Table (CBT)715, a Connection Data Table (CDT) 720, and a Connection Match Table(CMT) 725. Entries for a delegated connection within CBT 715, CDT 720,and CMT 725 can be written by CMD Unit 710. CMT 725 stores delegatedconnection identification information and CMT 725 is written to by CMDUnit 710 when a delegated connection is set up. In CMT 725, an entrycorresponding to a delegated connection maintains that correspondence aslong as the connection remains delegated or until the connection ends.An entry in CMT 725 includes a destination IP address, a source IPaddress, a source TCP port, a destination TCP port, and the like.

An entry in CDT 720 is initialized by CMD Unit 710 when a delegatedconnection is set up. An entry within CDT 720 includes delegatedconnection state information for a delegated connection, such as anexpected sequence number, an ACK number, timestamp data, a count ofunACKnowledged frames, and the like. Fields within the entry in CDT 720are read and optionally modified by Transmit Engine 320 when frames areconstructed for transmission on the delegated connection. Likewise,fields within the entry in CDT 720 are read and optionally modified byunits within Receive Engine 360 as incoming frames on the delegatedconnection are processed. An entry in CBT 715 is written with one ormore user buffer descriptors by CMD Unit 710 when a PRB command isreceived for a delegated connection. The user buffer information is readand optionally modified by a Buffer Upload Unit 745 within ReceiveEngine 360.

The delegated connection information has been distributed between CBT715, CDT 720, and CMT 725 in such a manner as to decouple accesses ofthe state information stored in CDT 720 from user buffer postingseffecting CBT 715. Furthermore, because the state information is updatedby Receive Engine 360 based on the most recently received frame,Transmit Engine 320 and TCP Stack 215 can access current stateinformation during frame construction. Likewise, because the stateinformation is also updated by Transmit Engine 320 based on the mostrecently transmitted frame, Receive Engine 360 and TCP Stack 215 canaccess up-to-date state information during frame processing.

Within Receive Interface 370, a buffer, Receive FIFO 730 buffersincoming frames. Receive Interface 370 outputs frames and valid frameindicators to a Pre-parse Unit 735 within Receive Engine 360. Pre-parseUnit 735 parses valid frames, producing partially parsed frames, andreads CMT 725 to determine whether or not the frame was received on adelegated connection. Pre-parse Unit 735 outputs the partially parsedframes to a Parsing Unit 740. Parsing Unit 740 determines a protocoltype for each partially parsed frame, e.g., TCP, UDP, IP, and the like,and optionally parses the partially parsed frames producing parsedframes and partially parsed frames. Parsing Unit 740 reads CDT 720,determines if one or more special cases exist, and outputs the partiallyparsed frames, parsed frames, or frames, to Buffer Upload Unit 745.Parsing Unit 740 also optionally sets notification flags, describedfurther herein, stored in a storage element, such as a register withinNotification Unit 750.

Buffer Upload Unit 745 reads CBT 715 and optionally writes CBT 715 andCDT 720. Buffer Upload Unit 745 uploads the frames, partially parsedframes, and parsed frames to System Memory 130 via DMA Engine 310.Buffer Upload Unit 745 specifies locations to write in System Memory 130based on data stored in a user buffer descriptor stored in CBT 715 or alegacy buffer descriptor received from Driver 255 via the ReceiveDescriptor Ring 621. Similarly, Transmit Engine 320 specifies locationsto read in System Memory 130 based on transmit buffer descriptorsreceived from Driver 255 via the Transmit Descriptor Ring 631.Notification Unit 750 outputs notifications to Driver 255 via DMA Engine310 to Notification Ring 611.

Delegated connection information for a limited number of connections isstored in CMT 725, and after the limited number is reached, connectioninformation for excess connections is stored only in CT 245 (in FIG. 2Aor FIG. 2B) within System Memory 130. In one embodiment, rather thanaccessing the connection information in CT 245 to process incoming andoutgoing frames for the excess connections, HOT Unit 250 uploadspartially processed frames to a legacy buffer in Driver Memory Space235. In another embodiment, HOT Unit 250 treats DCT 350 as a cache andaccesses CT 245 as needed to locate relevant connection data. TCP Stack215 completes processing of the partially processed frames independentof processing of additional incoming or outgoing frames performed by HOTUnit 250. Therefore, legacy processing of excess connections typicallyproceeds at a rate that is equal or better than processing of frames ina Computing System 200 without HOT Unit 250. The rate may be betterbecause the frames are partially processed by HOT Unit 250 and theresults of frame validation performed in Receive Interface 370 are alsouploaded to Driver Memory Space 235. Furthermore, legacy processing byDriver 255 and TCP Stack 215 can proceed concurrently with transmitprocessing by HOT Unit 250 or with receive processing by HOT Unit 250.

FIG. 8A is a flow diagram of method steps for processing a valid frame,in accordance with one embodiment of the present invention. In step 801a valid frame is received by Pre-parse Unit 735 within Receive Engine360. In step 803 Pre-parse Unit 735 determines if the valid frame is aTCP frame, and if not, in step 805 non-TCP processing, known to thoseskilled in the art is completed. In one embodiment, Receive Engine 360completes processing of received UDP frames. In another embodiment,Receive Engine 360 completes processing of other protocols. In yetanother embodiment, Receive Engine 360 uploads frames of other protocolsto Driver Memory Space 235 and notifies Driver 255.

If, in step 803, Pre-parse Unit 735 determines the valid frame is a TCPframe, then in step 807, Pre-parse Unit 735 reads one or more entriesfrom CMT 725. In step 809 Pre-parse Unit 735 determines if the TCPframe, hereafter referred to as “the frame,” was received on a delegatedconnection, i.e., if the frame matches an entry in CMT 725. Pre-parseUnit 735 extracts the destination IP address, the source IP address, thesource TCP port, and the destination TCP port from the frame and usesthese values to search for a matching entry in CMT 725. A matchindicates that the connection has been delegated. If, in step 809,Pre-parse Unit 735 determines the frame was not received on a delegatedconnection, then in step 813, legacy processing of the frame iscompleted. Pre-parse Unit 735 initiates legacy processing by outputtingthe frame to Buffer Upload Unit 745 via Parsing Unit 740 and indicatingthe frame was not received on a delegated connection. Buffer Upload Unit745 uploads the at least partially parsed frame to Driver Memory Space235 via DMA Engine 310 and notifies Driver 255 with a request for legacyprocessing, as described further herein.

If, in step 809, Pre-parse Unit 735 determines that the frame wasreceived on a delegated connection, then in step 811 Pre-parse Unit 735outputs the partially processed frame to Parsing Unit 740. In step 811Parsing Unit 740 parses the partially processed frame, producing aparsed frame and determines if there is a special case, e.g., IP or TCPoptions, invalid flags, or the like, and if so, in step 812 Parsing Unitoutputs the parsed frame to Buffer Upload Unit 745 indicating there is aspecial case. In step 812, Buffer Upload Unit 745 sets a “sync request”flag in an entry in CBT 720 corresponding to the delegated connectionand flushes any user buffer descriptors in the entry in CBT 715corresponding to the delegated connection. In step 813, Buffer UploadUnit 745 uploads the parsed frame to Driver Memory Space 235 via DMAEngine 310 and notifies Driver 255 with a request for legacy processing.Setting the “sync request” flag for a delegated connection in step 812indicates that the delegated connection is processed using legacyprocessing. Receive Engine 360 does not accept user buffer descriptorcommands for the delegated connection until the sync request flag iscleared by a future buffer posting event, as further described inrelation to FIG. 9A.

If, in step 811 Parsing Unit 740 determines there is not a special case,then in step 815 Parsing Unit 740 reads an entry in CDT 720corresponding to the delegated connection. In step 817 Parsing Unit 740and Buffer Upload Unit 745 determine which, if any, notification flagsstored in Notification Unit 750 are set, as further described inrelation to FIG. 9A. In step 819 Parsing Unit 740 determines if asequence number (SN) extracted from the TCP frame is not equal to asequence number (DCT SN) stored in the entry in CDT 720 corresponding tothe delegated connection, and if so, out-of-sequence recovery isrequested by Parsing Unit 740 in step 821. Out-of-sequence recovery isfurther described in relation to FIG. 8B.

If, in step 819, Parsing Unit 740 determines the SN is equal to the DCTSN, then in step 823 Parsing Unit 740 outputs the parsed frame to BufferUpload Unit 745. In step 823 Buffer Upload Unit 745 reads the entry inCBT 715 corresponding to the delegated connection. In step 825, BufferUpload Unit 745 determines if a user buffer is available. The term “userbuffer” is interchangeable with the term “HOT buffer”. If a HOT bufferis not available, then in step 827 Buffer Upload Unit 745 either waitsfor a HOT buffer to become available or uploads the parsed TCP frame toa legacy buffer via DMA Engine 310, as further described in relation toFIG. 8C.

If, in step 825, Buffer Upload Unit 745 determines a HOT buffer isavailable, then in step 829 Buffer Upload Unit 745 completes processingof the parsed frame and uploads at least a portion of the payload datato the HOT buffer, as further described in relation to FIG. 8D. In step831, after uploading a portion of the payload data to a HOT buffer,Buffer Upload Unit 745 determines if there is additional payload data inthe parsed frame, and, if so, repeats steps 825 and 829. If, in step831, Buffer Upload Unit 745 determines that all of the payload data hasbeen uploaded to one or more HOT buffers, then in step 833 Buffer UploadUnit determines if a TCP “push” flag in the parsed frame had beenasserted. If, in step 833, Buffer Upload Unit 745 determines the TCP“push” flag was asserted, Buffer Upload Unit 745 sets the “sync request”flag for the entry in CBT 715 corresponding to the delegated connectionand flushes any user buffer descriptors in the entry in CBT 715corresponding to the delegated connection. If, in step 833, BufferUpload Unit 745 determines the TCP “push” flag is not asserted, then theReceive Engine 360 proceeds to step 801.

FIG. 8B is a flow diagram of method steps for processing out-of-sequenceframes, in accordance with one embodiment of the present invention. Aspersons skilled in the art will understand, the method steps describedwith respect to FIG. 8B constitute one way of performing step 821 ofFIG. 8A. Out-of-sequence recovery handles cases including a SN that isgreater than what was expected based on the value stored in the DCT SN(e.g., resulting from one or more lost frames) or a SN that is less thana DCT SN (e.g., resulting from retransmission of a frame due to atransmit timeout or a lost ACK). When the SN is greater than the DCT SN,the Receive Engine 360 executes a “fast recovery” algorithm, includingtransmission of up to three consecutive identically constructed ACKs(each corresponding to last frame received in-sequence), invalidates(flushes) the user buffers for the delegated connection, and uploads theentire frame to one or more legacy buffers. When the SN is less than theDCT SN, the Receive Engine 360 transmits an ACK for the frame,invalidates the user buffers for the delegated connection, and uploadsthe entire frame to one or more legacy buffers.

In step 830 Parsing Unit 740 determines if the SN extracted from theframe is less than the DCT SN read from CDT 720 in step 815 of FIG. 8A,and if so, in step 832 Parsing Unit 740 signals Transmit Engine 320 togenerate an ACK for the frame. In step 832, Parsing Unit 740 alsooutputs the parsed frame to Buffer Upload Unit 745 and proceeds to step838. If, in step 830, Parsing Unit 740 determines the SN extracted fromthe frame is not less than the DCT SN, then in step 834, Parsing Unit740 determines if a “Fast ACK” value read from CDT 720 in step 815 isless than 3, and if so, Parsing Unit 740 signals to Transmit Engine 320to generate an ACK for the parsed frame in step 836. Also in step 836,Parsing Unit 740 outputs the parsed frame to Buffer Upload Unit 745 andindicates to Buffer Upload Unit 745 to increment the “Fast ACK” valuestored in CDT 720.

In step 838 Buffer Upload Unit 745 flushes any HOT buffers correspondingto the delegated connection stored in CBT 715. In step 840, BufferUpload Unit 745 sets a “sync request” flag corresponding to thedelegated connection in CBT 715 and optionally updates connection statedata for the delegated connection, e.g., Fast ACK, DCT SN, ACK number,and the like, stored in CDT 720. In step 813, Buffer Upload Unit 745uploads the parsed TCP frame to Driver Memory Space 235 via DMA Engine310 and notifies Driver 255 with a request for legacy processing.

FIG. 8C is a flow diagram of method steps for waiting for a user buffer,in accordance with one embodiment of the present invention. As personsskilled in the art will understand, the method steps described withrespect to FIG. 8C constitute one way of performing step 827 of FIG. 8A.Receive Engine 360 waits for a user buffer rather than uploading aparsed frame or partially parsed frame to a legacy buffer because datauploaded user buffers does not need to be copied from Driver MemorySpace 235 to Application Memory Space 227 by TCP Stack 215. Furthermore,once a delegated connection is processed using a legacy buffer, TCPStack 215 must respond to the “sync request” flag, resulting in the“sync request” flag being cleared, before a parsed frame or a partiallyparsed frame for the delegated connection will be uploaded to a userbuffer by the Receive Engine 360.

In step 850, Buffer Upload Unit 745 determines if a “request buffer”flag is set in the entry, read in step 823 of FIG. 8A, corresponding tothe delegated connection. If the “request buffer” flag is not set, thenin step 852 Buffer Upload Unit 745 sets the request buffer flag in theentry in CBT 715 corresponding to the delegated connection andinitializes the buffer request timer to a value stored in a register. Inan alternate embodiment the buffer request timer is initialized to avalue stored in the entry in CBT 715 corresponding to the delegatedconnection. If, in step 850, the Buffer Upload Unit 745 determines thatthe “request buffer” flag is set, then Buffer Upload Unit 745 proceedsto step 862.

In step 854 Buffer Upload Unit 745 uploads a number of bytes, determinedby a “startup limit” value to a legacy buffer via DMA Engine 310. Thestartup limit, initialized by TCP Stack 215 is stored in the entry inCDT 720 corresponding to the delegated connection. In step 856, BufferUpload Unit 745 sets the “request buffer” flag stored in NotificationUnit 750 and Notification Unit 750 issues a notification to Driver 255via the notification ring. The notification includes the same tag valuethat was used in the tag field from the associate legacy bufferdescriptor. Notification Unit 750 clears the notification flags aftersending the notification. Techniques known to those skilled in the artare used to ensure that the parsed frame is uploaded to Driver MemorySpace 235 before Driver 255 receives the corresponding notification.

In step 858 Buffer Upload Unit 745 determines if a value indicating the“fullness” of Receive FIFO 730 is greater than a limit, e.g., a “highwater” mark, and, if so Buffer Upload Unit 745 proceeds to step 862. Inone embodiment, the high water mark is fixed. In an alternateembodiment, the high water mark is stored in a register programmed byDriver 255. If, in step 858, Buffer Upload Unit 745 determines the valueindicating the “fullness” of Receive FIFO 730 is not greater than the“high water” mark, then in step 860 Buffer Upload Unit 745 determines ifa buffer request timer has expired. If, in step 860, Buffer Upload Unit745 determines the buffer request timer has expired, then in step 862Buffer Upload Unit 745 sets the “sync request” flag stored in CBT 715and the legacy flag stored in Notification Unit 750. In step 813, BufferUpload Unit 745 uploads the parsed frame to Driver Memory Space 235 viaDMA Engine 310. Notification Unit 750 issues a notification to Driver255 via the notification ring, Notification Unit 750 clears thenotification flags, and Receive Engine 360 returns to step 801 in FIG.8A. The notification includes the same tag value that was used in thetag field from the associated legacy buffer descriptor. Techniques knownto those skilled in the art are used to ensure that the parsed frame isuploaded to Driver Memory Space 235 before Driver 255 receives thecorresponding notification.

If, in step 860 Buffer Upload Unit 745 determines the buffer requesttimer has not expired, in step 864 Buffer Upload Unit 745 determines ifa user buffer is available, i.e., if Application Program has posted auser buffer via the command ring. If a user buffer is not available,Buffer Upload Unit 745 returns to step 858. If a user buffer isavailable, Buffer Upload Unit 745 completes processing of the parsedframe and uploads the payload data to the user buffer in step 829, asfurther described in relation to FIG. 8D. Following step 829, ReceiveEngine 360 returns to step 831 of FIG. 8A.

FIG. 8D is a flow diagram of method steps for completing HOT bufferprocessing, in accordance with one embodiment of the present invention.As persons skilled in the art will understand, the method stepsdescribed with respect to FIG. 8D constitute one way of performing step829 of FIG. 8A. When HOT Unit 250 receives incoming data, an ACK shouldbe sent to a sender (destination connection) to ensure that a receivewindow, indicating how much data may be sent to HOT Unit 250, remainsopen wide enough to permit saturation of the receive path. When receivedframes are not ACKnowledged in a timely manner, the receive window mayneed to be closed, else a retransmit timer within the sender may expire,causing the sender to retransmit one or more frames.

In addition to transmitting ACKs to the sender, Driver 255 is notifiedas frames are received by HOT Unit 250 based on sequence numbers,timers, and the like. CDT 720 is updated by increasing DCT SN by thereceived TCP payload size, a count of unACKnowledged frames isincremented, and the most recently received TCP timestamp extracted fromthe received frame is stored in CDT 720 for the delegated connection, ifthe TCP timestamp option was appropriately included in the receivedframe.

In step 876 Parsing Unit 740 determines if the count of unACKnowledgedframes is greater than an unACKnowledged frame limit, and if so,proceeds to step 880. The unACKnowledged frame limit is stored in CDT720 for the connection and is determined by TCP Stack 215. In analternate embodiment, Parsing Unit 740 determines if the count ofunACKnowledged frames received on the delegated connection is greaterthan or equal to the unACKnowledged frame limit in step 876. In anotheralternate embodiment, Buffer Upload Unit 745 determines if the count ofunACKnowledged frames is greater than the unACKnowledged frame limit.

If, in step 876, Parsing Unit 740 determines the count of unACKnowledgedframes is less than or equal to the unACKnowledged frame limit, thenParsing Unit 740 determines if a transmit timer has expired in step 878.A transmit ACK timer is configured to expire before a sender'sretransmit timer would expire, in order to minimize unnecessaryretransmissions due to the sender not receiving timely ACKs. In oneembodiment, the expiration period of the transmit ACK timer is aconstant for all delegated connections. In an alternate embodiment, theexpiration period of the transmit ACK timer may be programmed by TCPStack for each delegated connection.

If, in step 878 Parsing Unit 740 determines the transmit ACK timer hasexpired, then Parsing Unit 740 signals Transmit Engine 320 to generatean ACK for the parsed frame in step 880 and Transmit Engine 320 outputsthe parsed frame to Buffer Upload Unit 745. In step 882, Buffer UploadUnit 745 updates the unACKnowledged frame count stored in the entry inCDT 720 for the connection by setting it to zero and updates a “last ACKsent” value to the SN value extracted from the frame. Buffer Upload Unit745 also updates connection state data such as the incremental ACKnumber, the incremental sequence number, and the like, and resets thetransmit ACK timer before proceeding to step 886.

If, in step 878, Buffer Upload Unit 745 determines the transmit ACKtimer has not expired, then Buffer Upload Unit 745 updates the entrycorresponding to the delegated connection in CDT 720 in step 884, e.g.,by updating the count of unACKnowledged frames, and the like.

In step 886 the payload data are uploaded by Buffer Upload Unit 745 viaDMA Engine 310 to a HOT buffer TCP in Application Memory Space 227. Instep 888, Notification Unit 750 determines if any notification flags areset, and, if so, in step 890, Notification Unit 750 issues anotification to Driver 255 via the notification ring. Notification Unit750 constructs an event notification descriptor, including thenotification flags, the transmit window size, SN, the last ACK number,the TCP timestamp value, the tag value from the legacy descriptor, andthe like. Notification Unit 750 clears the notification flags aftersending the notification.

Notification Unit 750 outputs the event notification descriptor to DMAEngine 310 which transfers the event notification descriptor to anoffload event notification ring stored in Driver Memory Space 235. Theoffload event notification ring is organized as a circular queue in acontiguous memory block. HOT Unit 250 writes the offload eventnotification ring and Driver 255 reads the offload event notificationring. TCP Stack 215 may use data read from the offload eventnotification ring to update CT 245, thereby maintaining coherencebetween CT 245 and DCT 350. TCP Stack 215 may also maintain coherencebetween CT 245 and DCT 350 by uploading entries from CDT 715 to one ormore legacy buffers.

Following step 890, Receive Engine 360 returns to step 801 to processanother valid frame. If, in step 888, Notification Unit 750 determinesthat one or more notification flags are not set, then Receive Engine 360returns to step 801 to process another valid frame.

FIG. 9A is a flow diagram of method steps for determining notifications,in accordance with one embodiment of the present invention. As personsskilled in the art will understand, the method steps described withrespect to FIG. 9A constitute one way of performing step 817 of FIG. 8A.Rather than interrupting CPU 110 to inform TCP Stack 215 via Driver 255that each frame has been received by a destination, thresholds may beused to control the frequency of communicating sequence numbers receivedby HOT Unit 250 to Driver 255 or TCP Stack 215. Likewise, rather thaninterrupting CPU 110 to inform Driver 255 that ACKs have been receivedfor each transmitted frame, ACK thresholds or specific ACK numbers maybe used to control the communication of ACKs received by HOT Unit 250 toDriver 255.

Reducing the frequency of interrupts CPU 110 received during frameprocessing frees the CPU 110 to execute other applications, typicallyimproving performance of those applications by increasing the number ofapplication instructions CPU 110 executes. The thresholds permitflexibility in determining a balance between interrupts to notify TCPStack 215 of receive connection status and transmit connection status,for delegated connections.

In step 901 Parsing Unit 740 determines if the transmit window isshrinking from the right. Parsing Unit 740 determines the transmitwindow is shrinking from the right when an ACK number extracted from theframe summed with the receive window size extracted from the frame isless than a maximum transmit window size stored in CDT 720 for thedelegated connection. Buffer Upload Unit 745 updates the maximumtransmit window size stored in CDT 720 for the delegated connection withthe transmit window size extracted from the frame. If, in step 901,Parsing Unit 740 determines the transmit window is shrinking from theright, then in step 903, Parsing Unit 740 sets a transmit windownotification flag in Notification Unit 750.

In step 905, Parsing Unit 740 determines if duplicate ACKs (same ACKnumbers in one or more received frames) have been received, indicatingthat the destination is requesting retransmission of one or more frames.If, in step 905, Parsing Unit 740 determines duplicate ACKs have beenreceived, then in step 903, Parsing Unit 740 sets a “duplicate ACKnotification” flag in Notification Unit 750.

In step 907, Parsing Unit 740 determines if SN is greater than athreshold, e.g., limit, the threshold indicating an incremental sequencenumber. The incremental sequence number is initialized by TCP Stack 215when a delegated connection is set up and is updated by Buffer UploadUnit 745 whenever a notification is sent to Driver 255. In oneembodiment, the incremental sequence number is updated by increasing theincremental sequence number by a sequence increase value. The sequenceincrease value may be fixed or programmed by TCP Stack 215. If, in step907, Parsing Unit 740 determines SN is greater than the threshold, thena sequence number threshold flag is set in step 903.

In step 909, Parsing Unit 740 determines if a last ACK number (the mostadvanced ACK number received for the delegated connection) stored in CDT720 is greater than a limit, the limit indicating an incremental ACKnumber. The last ACK number is initialized by TCP Stack 215 when adelegated connection is set up and is updated by Buffer Upload Unit 745whenever an ACK is received. The incremental ACK number is initializedby TCP Stack 215 when a delegated connection is set up and is updated byBuffer Upload Unit 745 whenever a notification is sent to TCP Stack 215.In one embodiment, the incremental ACK number is updated by increasingthe incremental ACK number by an ACK increase value. The ACK increasevalue may be fixed or programmed by TCP Stack 215.

In step 909, Parsing Unit 740 may also determine if the last ACK numberstored in CDT 720 is greater than another limit, the other limitindicating a specific ACK number programmed by TCP Stack 215. If, instep 909, Parsing Unit 740 determines the last ACK number is greaterthan the limit (indicating an incremental ACK number) or the other limit(indicating a specific ACK number), then an ACK threshold flag is set instep 903.

In step 911, Parsing Unit 740 determines if one or more timers haveexpired. A receive ACK timer is configured to expire before TCP Stack's215 retransmit timer expires in order to minimize unnecessaryretransmissions. The expiration period of the receive ACK timer for adelegated connection stored in a register may be programmed by TCP Stack215 and may be based on a round trip time for the delegated connection.A receive SN timer is configured to notify TCP Stack 215 that data hasbeen received by HOT Unit 250. The expiration period of the receive SNtimer for a delegated connection stored in a register may be programmedby TCP Stack 215. In an alternate embodiment, the expiration periods ofthe receive ACK timer and the receive SN timer are stored in an entry inCMT 725 corresponding to a delegated connection.

If, in step 911, Parsing Unit 740 determines that a timer has expired,then a corresponding notification flag is updated in step 903 andParsing Unit 740 proceeds to step 913. For example, when the receive SNtimer expires, the “sequence number threshold” flag is set and when thereceive ACK timer expires, the “ACK threshold” flag is set. If, in step911, Receive Engine 360 determines none of the one or more timers hasexpired, then Parsing Unit 740 outputs the parsed frame to Buffer UploadUnit 745 in step 913 and Buffer Upload Unit 745 determines if the pushflag extracted from the frame has been asserted. If the push flag wasasserted, then a push notification flag is set in step 903 and BufferUpload Unit 745 proceeds to step 819 of FIG. 8A.

FIG. 9B is a flow diagram of method steps for synchronizing a userbuffer following legacy processing, in accordance with one embodiment ofthe present invention. As previously described, a delegated connectionwill be processed using legacy buffers when Parsing Unit 740 detects aframe with a sequence number greater than an expected sequence number,DCT SN. For example, when one or more frames are lost due to atransmission error. Notification Unit 750 requests legacy processing forthe connection and Buffer Upload Unit 745 invalidates the HOT buffersfor the connection. Because SN stored in CDT 720 is not changed, allsubsequent received frames will be considered to be out-of-sequenceuntil a retransmission occurs.

Until the retransmitted frame is received, Buffer Upload Unit 745uploads frames received for the connection to legacy buffers. TCP Stack215 copies the payload data from legacy buffers to user buffers. Whenthe retransmitted frame is uploaded to a legacy buffer, TCP Stack 215sends an ACK for all frames received in sequence. Transmit Engine 320updates the DCT SN stored in CDT 720 for the connection. When all of theretransmitted frames within a sequence have been uploaded to legacybuffers, TCP Stack 215 posts HOT buffers prior to sending the ACK.Posting the HOT buffers allows Buffer Upload Unit 745 to resumeprocessing incoming frames for the connection using HOT buffers withoutrequesting user buffers.

In step 930, CMD Unit 710 receives a PRB command from the command ringvia DMA Engine 310. The PRB command includes a DCT index correspondingto an entry for a connection, and a sync bit, among other fields. Instep 932, CMD Unit 710 reads CBT 715 using the index. In step 934, CMDUnit 710 determines if the sync request flag read from the entry in CBT715 is set, and if so, in step 936 CMD Unit 710 determines if the syncbit in the PRB command is set. If, in step 934, CMD Unit 710 determinesthe “sync request” flag read from the entry in CBT 715 is not set, thenCMD Unit 710 clears the entry's “sync request” flag in CBT 715 in step938, and proceeds to step 940. When the “sync request” flag is cleared,the connection may be processed using HOT buffers. If, in step 936, CMDUnit 710 determines the sync bit in the PRB command is not set, the“sync request” flag is not cleared and the connection continues to beprocessed using legacy processing.

Transmit Engine 320 includes subunits for offloading outbound frameprocessing from TCP Stack 215. For example, Transmit Engine 320 may beconfigured to perform TCP segmentation, compute TCP and IPv4 checksums,and edit outbound frames to piggyback ACKs and include the most recentstate data for a delegated connection (read from DCT 350). Updates toDCT 350 made by Driver 255 or Receive Engine 360 may be included intransmissions, as described further herein.

FIG. 10A illustrates a format used to represent data for transmission asthe data is transferred from System Memory 130 to HOT Unit 250 by DMAEngine 310 in accordance with one or more aspects of the presentinvention, for example during a “large send” transmission. Field 1007 isa medium-specific MAC header such as an Ethernet header. Field 1005 is aprototype header including a MAC header, an IP header, and a TCP headerincluding an SN, transmit ACK number, a TCP timestamp, and the like.Field 1010 is the data for transmission and is located in TCP StackMemory Space 225. The combination of Field 1007, Field 1005, and Field1010 resides in System Memory 130.

FIG. 10B illustrates a format used to represent data for transmission asthe data is transmitted from Transmit Engine 320 to Transmit Interface330 in accordance with one or more aspects of the present invention. DMAEngine 310 reads the format shown in FIG. 10A from System Memory Space130 and Transmit Engine 320 produces the format shown in FIG. 10B whensegmentation is enabled and portions of Field 1010 are included insegments, where each segment is a frame. Transmit Interface 330 outputsthe IP datagram format shown in FIG. 10B as frame. In an alternateembodiment TCP Stack 215 generates protocol headers and stores theprotocol headers in TCP Stack Memory Space 225. The protocol headers areread by HOT Unit 250 from TCP Stack Memory Space 225, and the data fortransmission are read by HOT Unit 250 from Application Memory Space 227.

Field 1015 is an IP header, Field 1020 is a TCP header, and Field 1025is segmented data. As persons skilled in the art will recognize, theformat shown in FIG. 10B is a TCP-compliant format. The TCP headerincludes a transmit ACK number, a transmit SN, and the like. Thesegmented data is a portion of the data for transmission in Field 1010.Field 1030 is another TCP header, including an optionally updatedtransmit ACK number, an updated transmit SN, and the like. The updatedtransmit SN is increased by the amount of data bytes that were includedin the previous segment, which is the same as the difference between themaximum frame size and the data link, network, and transport layerheader sizes. Field 1035 is segmented data which is another portion ofthe data for transmission in Field 1010.

FIG. 11A is a flow diagram of method steps for segmenting an outboundframe represented in the format shown in FIG. 10A into segmentsincluding editing the outbound frame in accordance with one embodimentof the present invention. In step 1101 DMA Engine 310 receives atransmit descriptor from TCP Stack 215 via Driver 255. The transmitdescriptor includes a physical address of the location a transmit bufferstored in System Memory 130, the transmit buffer including a prototypeheader and data for transmission. The transmit descriptor also includescontrol bits specifying processing options, an optional DCT index,control bits specifying transmission options, and the like.

In step 1103, DMA Engine 310 reads the transmit buffer and outputs thetransmit descriptor and transmit buffer to Transmit Engine 320. In step1109, Transmit Engine 320 computes an IP checksum based on IP headerdata extracted from the prototype header. In step 1111, Transmit Engine320 determines a portion of the data for transmission included in thetransmit buffer based on the maximum segment size (set by thedestination during connection setup) after segmentation. In step 1113,Transmit Engine 320 constructs a segment for transmission, as describedfurther herein with regard to FIG. 11B.

In step 1131, Transmit Engine 320 computes a TCP checksum based on TCPheader data extracted from the prototype header, connection state dataread from DCT 350, and the portion of data for transmission in thecurrent frame. The calculated checksum is stored in the frame's TCPheader. In step 1133, Transmit Engine 320 updates a transmit SN storedin DCT 350 for the delegated connection by increasing the transmit SN bythe difference between the size (in bytes) of the data included in theframe and the header sizes. In step 1135, Transmit Engine 320 outputs aconstructed frame, including a computed TCP checksum, to TransmitInterface 330. Transmit Interface 330 outputs the constructed frame.

FIG. 11B is a flow diagram of method steps for constructing the outboundframe, in accordance with one embodiment of the present invention. Aspersons skilled in the art will understand, the method steps describedwith respect to FIG. 11B constitute one way of performing step 1113 ofFIG. 11A. The outbound frame is constructed using connection state datastored in CDT 720; consequently the outbound frame includes the mostup-to-date state data for a connection such as an ACK numbercorresponding to the most recently received frame. During transmission,including during segmentation, ACKs are “piggybacked” if possible, i.e.,included in the frame output for transmission rather than waiting tooutput discrete ACKs until after a frame (large send) has beencompletely segmented and transmitted. Timely ACKs ensure that thereceive window seen by the sender remains open, resulting in the sendercontinuing to transmit data. Additionally, deferring ACK transmissionuntil a large send is complete may result in wasteful retransmissions bythe sender when the sender's retransmit timer expires, or may result inunnecessary burstiness in the received data stream due to ACKs beingdelayed to only occur between “large sends”.

In step 1115, Transmit Engine 320 uses the DCT index received in step1101 with the transmission request to determine if the transmissionrequest corresponds to a delegated connection, and, if it does not,proceeds to step 1131 of FIG. 11A. Otherwise, in step 1117, TransmitEngine 320 accesses CDT 720 using the DCT index received in step 1101 toobtain connection state data for the delegated connection. In step 1119,Transmit Engine 320 determines a transmit SN for the constructed frame.When the SN received from TCP Stack 215 is later in the data stream thanthe transmit SN stored for the connection in CDT 720, Transmit Engine320 sets the transmit SN to the SN received from TCP Stack 215.

In step 1121, Transmit Engine 320 examines the control bits specifyingprocessing options and determines if TCP Stack 215 requests TransmitEngine 320 to save the SN of the first byte of the frame in CDT 720. Thesaved SN is used in step 907 of FIG. 9A to control notification of TCPStack 215 when an ACK corresponding to the saved SN is received. If, instep 1121, Transmit Engine 320 determines TCP Stack 215 requestsnotification for a specific ACK number, then in step 1123 TransmitEngine 320 saves the SN as a specific ACK number in CDT 720 for theconnection.

In step 1125, Transmit Engine 320 determines an ACK number for theconstructed frame. When the ACK number received from TCP Stack 215 islater in the data stream than the DCT SN stored for the connection,Transmit Engine 320 sets the DCT SN to the ACK number received from TCPStack 215. Transmit Engine 320 also sets the last ACK number stored forthe connection in CDT 720 to the larger of the DCT SN or the ACK numberreceived from TCP Stack 215.

In step 1127, Transmit Engine 320 determines if the TCP timestamp optionis enabled by examining the connection state data stored for thedelegated connection in CDT 720. When the TCP timestamp option is notenabled, Transmit Engine proceeds to step 1131 of FIG. 11A. Otherwise,in step 1129, Transmit Engine 320 includes the current value of a freerunning timer in the TCP header of the constructed frame. TransmitEngine 320 also includes the greater of a timestamp received from TCPStack 215 and a timestamp stored for the connection (most recentlyreceived timestamp) in CDT 720. When the timestamp received from TCPStack 215 is greater than the timestamp stored for the connection, thetimestamp stored for the connection is set to the timestamp receivedfrom TCP Stack 215. Transmit Engine 320 proceeds to step 1131 to computethe TCP checksum for the constructed frame.

FIG. 11C is a flow diagram of method steps for generating ACKs forinclusion in a transmission, i.e., piggybacking, in accordance with oneembodiment of the present invention. The method illustrated in FIG. 11Cis completed by Receive Engine 360 as frames are received. In step 1145,Receive Engine 360 receives a sequential TCP frame for a delegatedconnection. In step 1147, Receive Engine 360 updates connection statedata, e.g., TCP timestamp, SN, transmit window size, and the like, inDCT 350 corresponding to the delegated connection. DCT SN is updated tothe next expected incoming SN.

In step 1149, Receive Engine 360 computes an ACK difference that is thedifference between the SN and the last ACK number (read from DCT 350).In step 1151 Receive Engine 360 determines if the ACK difference isgreater than a limit, the limit programmed by TCP Stack 215 to triggeran ACK to a received frame. If the ACK difference is greater than thelimit, Receive Engine 360 proceeds to step 1157. Otherwise, in step1153, Receive Engine 360 determines if the DCT SN is greater than athreshold, the threshold being an incremental sequence number or aspecific sequence number. If the DCT SN is greater than the threshold,Receive Engine 360 proceeds to step 1157. Otherwise, in step 1155,Receive Engine 360 determines if the previously described transmit ACKtimer has expired, and, if not, the transmit ACK timer and theunACKnowledged count is updated. If, in step 1155, Receive Engine 360determines the transmit ACK timer has expired, then in step 1157 ReceiveEngine 360 updates connection state data stored in DCT 350 for thedelegated connection, e.g., clearing the unACKnowledged count, updatingthe last ACKnowledged number, updating the incremental sequence number,and the like. Receive Engine 360 also resets the transmit ACK timer. Instep 1159, Receive Engine 360 signals Transmit Engine 320 to include anACK in a frame for transmission, i.e., by piggyback an ACK.

HOT Unit 350 offloads TCP processing for received valid TCP frames fordelegated connections while permitting flexibility for Driver 255 or TCPStack 215 to determine thresholds for interrupts based on received ACKsand timers. The thresholds may be used to reduce interrupts, freeing CPU110 to process other applications. Furthermore, HOT Unit 350 generatesACKs for transmission and edits outbound frames to piggyback ACKs, tocompute TCP and IPv4 checksums, and to perform TCP segmentation. Timelygeneration and transmission of ACKs to a sender may keep the receivewindow open, improving bandwidth utilization and reducing unnecessaryretransmissions during unidirectional and bidirectional communication.Finally, payload data uploads to user buffers in Application MemorySpace 227 reduces the need to copy data from Driver Memory Space 235 toApplication Memory Space 227. When user buffers are not available for adelegated connection and Receive FIFO 730 is full, legacy buffers may beused to upload received frames rather than not accepting incoming data.HOT Unit 250 does not rely on large amounts of dedicated memory or adedicated processor while providing offloading for some TCP processingfrom CPU 110. Hot Unit 250 also offloads some TCP processing from a hostprocessor and handles excess connections while accepting incoming data.

The invention has been described above with reference to specificembodiments. It will, however, be evident that various modifications andchanges may be made thereto without departing from the broader spiritand scope of the invention as set forth in the appended claims. Theforegoing description and drawings are, accordingly, to be regarded inan illustrative rather than a restrictive sense. The listing of steps inmethod claims do not imply performing the steps in any particular order,unless explicitly stated in the claim. Within the claims, elementlettering (e.g., “a)”, “b)”, “i)”, “ii)”, etc.) does not indicate anyspecific order for carrying out steps or other operations; the letteringis included to simplify referring to those elements.

1. A method of setting up a delegated connection, the method comprising:designating a first portion of a system memory within a first computingsystem for storage of frame payload data in legacy buffers, wherein thefirst portion of the system memory is allocated to a software driverconfigured to communicate between a dedicated hardware offload unit anda TCP stack; designating a second portion of the system memory forstorage of frame payload data in user buffers, wherein the secondportion of the system memory is allocated to an application program;establishing a TCP connection between the first computing system and asecond computing system; determining whether or not to delegate the TCPconnection for processing by the dedicated hardware offload unit tooffload the TCP connection processing from a CPU of the first computingsystem; setting up an entry in a delegated connection table upondetermining to delegate the TCP connection; receiving a frame for thedelegated connection and determining a user buffer is available forstorage of frame payload data; and uploading a portion of the frame to alocation in the second portion of the system memory that is specified inthe user buffer information.
 2. The method of claim 1, wherein the stepof determining is based on at least one characteristic of the TCPconnection.
 3. The method of claim 2, wherein the characteristic is apriority specified for the TCP connection.
 4. The method of claim 2,wherein the at least one characteristic is a duration of the TCPconnection.
 5. The method of claim 2, wherein the at least onecharacteristic is a frame rate of the TCP connection.
 6. The method ofclaim 1, further comprising transferring user buffer information for thedelegated connection to the hardware.
 7. A system for setting up adelegated connection, the system comprising: means for designating afirst portion of a system memory within a first computing system forstorage of frame payload data in legacy buffers, wherein the firstportion of the system memory is allocated to a software driverconfigured to communicate between a dedicated hardware offload unit anda TCP stack; means for designating a second portion of the system memoryfor storage of frame payload data in user buffers, wherein the secondportion of the system memory is allocated to an application program;means for establishing a TCP connection between the first computingsystem and a second computing system; means for determining whether ornot to delegate the TCP connection for processing by the dedicatedhardware offload unit to offload the TCP connection processing from aCPU of the first computing system; and means for setting up an entry ina delegated connection table upon determining to delegate the TCPconnection; means for receiving a frame for the delegated connection anddetermining a user buffer is available for storage of frame payloaddata; and means for uploading a portion of the frame to a location inthe second portion of the system memory that is specified in the userbuffer information.
 8. The system of claim 7, further comprising meansfor transferring user buffer information for the delegated connection tothe dedicated hardware offload unit.
 9. The system of claim 7, furthercomprising means for setting a maximum segment size.
 10. The system ofclaim 7, further comprising means for enabling and disablingacknowledgement coalescing.
 11. A method of setting up a delegatedconnection, the method comprising: designating a first portion of asystem memory within a first computing system for storage of framepayload data in legacy buffers, wherein the first portion of the systemmemory is allocated to a software driver configured to communicatebetween a dedicated hardware offload unit and a TCP stack; designating asecond portion of the system memory for storage of frame payload data inuser buffers, wherein the second portion of the system memory isallocated to an application program; establishing a TCP connectionbetween the first computing system and a second computing system; anddetermining whether or not to delegate the TCP connection for processingby the dedicated hardware offload unit to offload the TCP connectionprocessing from a CPU of the first computing system; setting up an entryin a delegated connection table upon determining to delegate the TCPconnection; receiving a frame for the delegated connection anddetermining a user buffer is not available; and uploading a portion ofthe frame to a legacy buffer in the first portion of the system memory.12. The method of claim 11, wherein the step of determining is based onat least one characteristic of the TCP connection.
 13. The method ofclaim 12, wherein the characteristic is a priority specified for the TCPconnection.
 14. The method of claim 12, wherein the at least onecharacteristic is a duration of the TCP connection.
 15. The method ofclaim 12, wherein the at least one characteristic is a frame rate of theTCP connection.
 16. The method of claim 11, further comprisingtransferring user buffer information for the delegated connection to thehardware.
 17. A system for setting up a delegated connection, the systemcomprising: means for designating a first portion of a system memorywithin a first computing system for storage of frame payload data inlegacy buffers, wherein the first portion of the system memory isallocated to a software driver configured to communicate between adedicated hardware offload unit and a TCP stack; means for designating asecond portion of the system memory for storage of frame payload data inuser buffers, wherein the second portion of the system memory isallocated to an application program; means for establishing a TCPconnection between the first computing system and a second computingsystem; means for determining whether or not to delegate the TCPconnection for processing by the dedicated hardware offload unit tooffload the TCP connection processing from a CPU of the first computingsystem; means for setting up an entry in a delegated connection tableupon determining to delegate the TCP connection; means for receiving aframe for the delegated connection and determining a user buffer is notavailable; and means for uploading a portion of the frame to a legacybuffer in the first portion of the system memory.
 18. The system ofclaim 17, further comprising means for transferring user bufferinformation for the delegated connection to the dedicated hardwareoffload unit.
 19. The system of claim 17, further comprising means forsetting a maximum segment size.
 20. The system of claim 17, furthercomprising means for enabling and disabling acknowledgement coalescing.